Merged
Conversation
…istencies
- Fix subject-verb agreement in casb-dlp.mdx ('contains' -> 'contain')
- Align troubleshoot navigation path to canonical 'Cloud & SaaS findings > Integrations'
- Align toggle label to 'Scan for findings' per manage-integrations partial
- Replace undocumented 'Suppress' action with cross-link to ignore/hide workflow
- Apply same fixes to duplicate troubleshoot file in integrations folder
Oxyjun
requested review from
a team,
Maddy-Cloudflare,
codyanthony850 and
ranbel
as code owners
Contributor
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
Contributor
- Split long CASB intro sentence and explain 'API-driven' inline (index.mdx) - Add DLP profile parenthetical definition (casb-dlp.mdx) - Add caution callout for full-scan vs incremental-scan distinction (casb-dlp.mdx) - Rephrase ambiguous Java/R minimum size limitation (casb-dlp.mdx) - Add OCR cross-link to clarify that CASB does not scan images but DLP does via Gateway (casb-dlp.mdx) - Add parenthetical for 'data at rest' (manage-findings.mdx) - Add ignore vs hide comparison before procedures (manage-findings.mdx) - Clarify Failed vs Rejected remediation statuses (manage-findings.mdx) - Rewrite Gateway policy intro to bridge CASB-to-Gateway concept (manage-findings.mdx) - Add finding ID location hint (troubleshoot-casb.mdx)
| - [Text-based files](/cloudflare-one/data-loss-prevention/#supported-file-types) such as documents, spreadsheets, and PDFs. Images are not supported. | ||
| - Files less than or equal 100 MB in size. | ||
| - Source code with a minimum size of 5 KB for Java and R. | ||
| - [Text-based files](/cloudflare-one/data-loss-prevention/#supported-file-types) such as documents, spreadsheets, and PDFs. Images are not scanned by CASB. For image scanning via inline traffic inspection, refer to [Optical Character Recognition (OCR)](/cloudflare-one/data-loss-prevention/dlp-profiles/advanced-settings/#optical-character-recognition-ocr). |
Contributor
There was a problem hiding this comment.
OCR now works in CASB, we can remove this limitation
caley-b
approved these changes
Apr 10, 2026
Contributor
caley-b
left a comment
caley-b
left a comment
There was a problem hiding this comment.
Some changes to consider post-feedback from Alexa.
| To trigger a new scan: | ||
|
|
||
| 1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Integrations** > **Cloud & SaaS integrations**. | ||
| 1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Integrations**. |
Contributor
There was a problem hiding this comment.
Should we go ahead and update the link to go In the Cloudflare dashboard, go to Zero Trust...
But I actually think the old text is the correct way of navigating there. @alexamavrogianis do you agree? If we drop them in the Cloud & SaaS findings area, they will then have to go to Cloud & SaaS findings > Overview >> Manage integrations >> View integrations ---> Integrations
Contributor
There was a problem hiding this comment.
Yes, good catch. The Integrations > Cloud & SaaS integrations is more effective nav structure
| To trigger a new scan: | ||
|
|
||
| 1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Integrations** > **Cloud & SaaS integrations**. | ||
| 1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Integrations**. |
Contributor
There was a problem hiding this comment.
Same thing here potentially as above.
|
|
||
| ### Ignore a finding | ||
|
|
||
| 1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Posture Findings**. |
Contributor
There was a problem hiding this comment.
Suggested change
| 1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Posture Findings**. | |
| 1. In the [Cloudflare dashboard](https://dash.cloudflare.com), go to **Zero Trust** > **Cloud & SaaS findings** > **Posture Findings**. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes grammar, navigation path, and terminology inconsistencies across CASB documentation, identified during an ELI5 clarity review of the
cloud-and-saas-findings/folder.casb-dlp.mdx): "files stored in a SaaS application contains" → "contain" (subject-verb agreement).troubleshoot-casb.mdx,integrations/.../casb.mdx): Changed**Integrations** > **Cloud & SaaS**to**Cloud & SaaS findings** > **Integrations**to match the canonical path used inmanage-findings.mdx,casb-dlp.mdx, and themanage-integrationspartial.troubleshoot-casb.mdx,integrations/.../casb.mdx): Changed**Findings scanning**to**Scan for findings**to match themanage-integrationspartial. Also removed an extra step ("Go to CASB") not present in the partial.troubleshoot-casb.mdx,integrations/.../casb.mdx): Replaced the undocumented "Suppress" action with a cross-link to the ignore/hide workflow documented inmanage-findings.mdx.